Test results of 5MHz SPI lines captured at 20MHz sampling rate.

USB enumeration with VID 0x04B4 and PID 0x4907

Please provide an open source firmware and open source code for uploading the firmware.

Hi Stefan,
Please find attached open source firmware for the usbsniffer/protocolanalyzer.
We are planning for release in WW17-20 just like the one below:
https://github.com/Infineon/mtb-example-fx2g3-slave-fifo-in
mtb-example-fx2g3-protocol-analyzer.zip

For firmware update we use USB FX Control Center windows application
https://softwaretools.infineon.com/tools/com.ifx.tb.tool.ezusbfxcontrolcenter

Regards,
Javeed

1. Windows only tool for flashing -> nogo
2. Unclear license - the usbfxstack dependency has an EULA which is not compatible with the Apache 2.0 license. Clear this mess up.

Specifically:

• The firmware must be redistributable without any limitations. Any requirements to tie the firmware (in source or binary form) to a specific product, or to a specific vendor, must be removed. (Such a requirement can not enforced when redistributing, only by not redistributing at all).
• The firmware must be buildable from the sources, and the sources must be complete (references to public git repositories are fine in general, but should (additionally) use standard URLs, e.g. using http(s) schemes.
• The toolchain must be available without any restrictions. This includes (at least) compiler and flashing routines.

You are free to provide additional tools, e.g. a Windows only GUI application. But you must at least provide a command line flashing tool (in source form), or an equivalent protocol description.

@javeed786Infineon Is the firmware stored in the volatile or non-volatile memory? If it's in non-volatile memory and sigrok does not need to upload it, I think this would be acceptable - as all the sigrok code is GPL licensed based on the file headers.

@StefanBruens While I agree that the upload process MUST be opensource and included in libsigrok if the memory is volatile, I don't necessarily think the firmware itself needs to be opensource or redistributable. I'm basing this on the documentation of various devices supported by sigrok that use non-free firmware or FPGA bitstreams. These are not distributed with sigrok, but documentation and tools exist that allow user to extract them to use with their device. I'm not sure if the policy changed since these were merged, but TBH it would not make sense - I have yet to see an oscilloscope with fully opensource firmware from a big player (and with big specs), and sigrok supports many of these.

The only showstopper would be if the firmware is volatile and needs to be uploaded on windows before every use, using a proprietary application. This would not really meet the current standard for device drivers.